Scheduling management system and its process control method

ABSTRACT

A simple and easy-to-memorize operation method for a scheduling management system is provided to perform main tasks such as referring to schedules of a selected member or a selected date. A software component indicating a schedule, a member, or a date is moved to any one of components constituting a GUI screen, and when the software component is superposed upon another component, the motion destination component constituting the GUI screen judges the type of the superposed software component to select a process to be performed. Main tasks can be performed by a simple operation method through superposition of software components.

BACKGROUND OF THE INVENTION

The present invention relates to a scheduling management system and moreparticularly to a process using cooperation between software components.

In a conventional scheduling management system, for example, asdisclosed in JP-A-1-173259, when some task is to be performed, it isnecessary to designate a task by using an icon or menu displayed on ascreen. In a recent scheduling management system, the number of iconsand menus is increasing as the functions of the system become abundant.It is therefore cumbersome to find an icon or menu to be designated whensome task is performed. It is also very tired to memorize the layout ofmenus and icons.

Most of a conventional scheduling management system request a user toselect a process to be performed by using a menu or the like, even ifthe process is a main process having a high use frequency such asreference to scheduling data of a member and reference to schedulingdata of a specific date, and the user is requested to perform cumbersomeoperations. Since most of main processes are selected by using a menu orthe like, it is necessary to memorize which menu is positioned in whatarea, and it takes a long time to become accustomed with operations.

As above, a conventional scheduling management system does not considermuch the operation performance of the system. Therefore it is difficultto understand the operation method and it takes a labor until a userbecomes accustomed with the operations.

SUMMARY OF THE INVENTION

It is an object of the present invention to solve the above problems andprovide simplified scheduling operation means.

A scheduling management system of this invention comprises: a schedulingdata storage device for storing scheduling data; a member informationstorage device for storing member information; a calendar informationstorage device for storing calendar information; a display device fordisplaying a GUI screen containing a plurality of components; an inputdevice such as a pointing device for designating an arbitrary positionon the GUI screen; and an inter-component communication control unitfor, if a movable software component on a certain component constitutingthe GUI screen is selected with the input device and is moved andsuperposed upon another component constituting the GUI screen, notifyingthe other motion destination component of the superposed softwarecomponent, wherein when the software component on one componentconstituting the GUI screen is superposed on another component, aprocess is controlled in accordance with the type of the softwarecomponent notified by the inter-component communication control unit.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram showing the configuration of a scheduling managementsystem according to an embodiment of the invention.

FIG. 2 is a diagram showing the data structure of member information.

FIG. 3 is a diagram showing the structure of scheduling data stored in aschedule storage device.

FIG. 4 is a diagram showing the structure of scheduling data stored in ascheduling data storage buffer.

FIGS. 5A and 5B are diagrams showing the data structures of visitingsite information and work matter information stored in a visitingsite/work matter storage device.

FIGS. 6A and 6B are diagrams showing the data structures of visitingsite information and work matter information stored in a visitingsite/work matter storage buffer.

FIG. 7 shows an example of a displayed member schedule.

FIG. 8 shows an example of a display incorporating visiting siteinformation.

FIG. 9 is a flow chart illustrating a process to be executed by aninter-component communication control unit.

FIG. 10 is a flow chart illustrating a process to be executed by aschedule display area component.

FIG. 11 is a flow chart illustrating a process to be executed by amember select component.

FIG. 12 is a flow chart illustrating a process to be executed by acalendar component.

FIG. 13 is a flow chart illustrating a process to be executed by avisiting site/work matter incorporating component.

FIG. 14 is a flow chart illustrating a member schedule referenceprocess.

FIG. 15 is a flow chart illustrating a date schedule reference process.

FIG. 16 is a flow chart illustrating a process of incorporating visitingsite information when new scheduling data is registered.

FIG. 17 is a flow chart illustrating a process of incorporating workmatter information when new scheduling data is registered.

FIG. 18 is a flow chart illustrating a process of deleting a memberschedule selected from a scheduling screen.

FIG. 19 is a flow chart illustrating a process of referring to theschedule of selected member on selected date.

FIG. 20 is a flow chart illustrating a process of copying schedules to aselected date.

FIG. 21 is a flow chart illustrating a visiting site/work matter.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1 is a diagram showing the configuration of a scheduling managementsystem according to an embodiment of the invention. The schedulingmanagement system includes an input device 101 such as a pointing devicefor inputting position information, a display unit 102, a memberinformation storage device 103, a calendar information storage device104, a scheduling data storage device 105, a visiting site/work matterstorage device 106, and a processor unit 107.

The member information storage device 103 stores, as shown in FIG. 2,member information constituted of items including a user ID 201, a username 202, a member type 203, and a parent ID 204. The member type 203 isa flag for judging whether the member is an individual or a group whichis a collection of individuals. The parent ID 204 is an item necessaryfor hierarchically managing the member information. For example, thehierarchical structure of members shown in FIG. 7 on a member selectcomponent 701 can be expressed by the data structure shown in FIG. 2.

The calendar storage device 104 stores calendar information.

The scheduling data storage device 105 stores, as shown in FIG. 3,scheduling data constituted of items including a user ID 301, a date302, a start time 303, an end time 304, a work matter 305, and avisiting site 306. The user ID 301 is an item indicating an owner ofschedules. The visiting site 305 is an item indicating a site where thework matter of a schedule is executed.

The visiting site/work matter information storage device 106 stores, asshown in FIG. 5A, visiting site information containing a user ID 501 anda visiting site 502 and work matter information containing a user ID 504and a work matter 503. If visiting site information and work matterinformation frequently used are registered in advance, such informationcan be incorporated when a new schedule is registered, so that the samevisiting site and work matter are not necessary to enter from akeyboard.

Next, the processor unit 107 of the scheduling management system will bedescribed. The processor unit 107 includes an input/output control unit108, an inter-component communication control unit 109, a member electcomponent 110, a calendar component 111, a chedule display areacomponent 112, and a visiting site/work matter incorporating component113.

The input/output control unit 108 supplies the processor unit 107 withinformation entered from the put device 101 such as a pointing device,and displays data supplied from the processor unit on the display unit102.

The inter-component communication control unit 109 has a function ofinforming, when a software component constituting a GUI screen is movedand superposed upon another software component, that the softwarecomponent was superposed upon the partner software component. With thisfunction, cooperation between components constituting the GUI screen canbe achieved.

The member select component 110 includes a member information storagebuffer 114, a member information management unit 115, and a judgementprocess unit (1) 116 for judging a superposed software component. Themember information storage buffer 114 temporarily stores memberinformation. The member information management unit 115 acquires memberinformation stored in the member information storage device 103 such asshown in FIG. 2, and stores the acquired member information in themember information storage buffer 114. The member information managementunit 115 also performs a process of hierarchically displaying thesoftware component representing the member information stored in themember information storage buffer 114, on the member select components701 as shown in FIG. 7. Reference numeral 704 represents a softwarecomponent showing group members, and reference numeral 705 represents asoftware component showing individual members. Upon a notice of asoftware component superposed upon the member select component from theinter-component communication control unit 109, the judging process unit(1) 116 for judging a superposed software component selects a process inaccordance with the type of the notified software component.

The calendar component 111 includes a calendar information storagebuffer 117, a calendar information management unit 118, and a judgingprocess unit (2) 119 for judging a superposed software component. Thecalendar information storage buffer 117 temporarily stores calendarinformation including year, month, day, and day of the week. Thecalendar information management unit 118 acquires calendar informationfrom the calendar information storage device 104 and stores it in thecalendar information storage buffer 117. The calendar informationmanagement unit 118 performs a process of displaying in a calendarformat the software component representing date information stored inthe calendar information storage buffer 117, on the calendar component702 such as shown in FIG. 7. Reference numeral 706 represents a softwarecomponent showing date information. Upon a notice of a softwarecomponent superposed upon the calendar component from theinter-component communication control unit 109, the judging process unit(2) 119 for judging a superposed software component selects a process inaccordance with the type of the notified software component.

The schedule display area component 112 includes a scheduling datastorage buffer 120, a scheduling data management unit 121, a user IDstorage buffer 122, a judgement process unit (3) 123 for judging asuperposed software component, and a default value setting unit 127. Thescheduling data storage buffer 120 temporarily stores scheduling dataacquired by the scheduling data management unit 121 from the schedulingdata storage device 105 and added with a new item of operation privilegesuch as shown in FIG. 4. The operation privilege 401 is an item used forsetting whether a privilege of changing or deleting the scheduling datais given to a user. The scheduling data management unit 121 performs aprocess of displaying the software component representing the schedulingdata stored in the scheduling data storage buffer 120, on the schedulescreen 707 of the schedule display area component 703 such as shown inFIG. 7. The software component representing the member whose schedule isto be referred to is also displayed on the schedule display 707. Theschedule display area component 703 shown in FIG. 7 is a display exampleof the scheduling data such as shown in FIG. 4 and stored in thescheduling data storage buffer 120. Reference numerals 710 and 711represent software components showing the scheduling data of Mr. A andMr. B. Reference numerals 708 and 709 represent software componentsshowing the members Mr. A and Mr. B. The scheduling data management unit121 also performs processes regarding schedule reference, registration,change, and deletion. The user ID storage buffer 122 temporarily storesa user ID entered when the user starts using the scheduling managementsystem.

This user ID is used when the operation privilege 401 of the schedulingdata is set or in other cases. Generally, the schedule operationprivilege 401 is set by considering whether the schedule is owned by theuser. It is therefore necessary for the system to know who is the user.Upon a notice of a software component superposed upon the scheduledisplay area component from the inter-component communication controlunit 109, the judging process unit (3) 123 for judging a superposedsoftware component selects a process in accordance with the type of thenotified software component. The default value setting unit 127 setsdefault values of a member and date and a rule for determining a defaultvalue, if the member and date are not designated when the schedulingdata is referred to, registered, copied, or moved. The default date maybe a current date. When selected scheduling data is registered in theschedule of other users, the default date may be the date information ofthe selected scheduling data. The default member may be a user, a memberdisplayed in the schedule screen 707, or the like. The default membermay be an owner of the selected schedule or the like when the scheduleis copied or moved.

The visiting site/work matter registering component 113 includes avisiting site/work matter storage buffer 124, a visiting site/workmatter management unit 125, and a judgment process unit (4) 126 forjudging a superposed software components. The visiting site/work matterstorage buffer 124 temporarily stores visiting site information and workmatter information. The visiting site/work matter management unit 125acquires the visiting site information and work matter informationincluding user ID from the visiting site/work matter storage device andstores it in the visiting site/work matter buffer 124. The visitingsite/work matter management unit 125 also performs a process ofdisplaying the software component representing the visiting siteinformation and work matter information stored in the visiting site/workmatter storage buffer 124, on the visiting site/work matter component801 such as shown in FIG. 8. For example, if the user ID is “USER001”,the visiting site information of the item numbers 1 to 3 in FIG. 5Acontaining the user ID “USER001” and the work matter information of theitem numbers 1 to 3 in FIG. 5B containing the user ID “USER001” areacquired from the visiting site/work matter information storing device106 storing the visiting site information shown in FIG. 5A and the workmatter information shown in FIG. 5B, and the acquired information isstored in the visiting site/work matter storage buffer 124. The storedvisiting site information of the item numbers 1 to 3 shown in FIG. 6Aand the stored work matter information of the item numbers 1 to 3 shownin FIG. 6B are displayed on the visiting site/work matter component 801such as shown in FIG. 8. Upon a notice of a software componentsuperposed upon the visiting site/work matter components from theinter-component communication control unit 109, the judging process unit(4) 126 for judging a superposed software component selects a process inaccordance with the type of the notified software component.

Next, the operation of the scheduling management system of theembodiment will be described in detail with reference to FIGS. 9 to 21.

First, with reference to FIG. 9, a process to be executed by theinter-component communication control unit 109 will be described. If asoftware component is superposed on any one of components constitutingthe GUI screen by using the input device 101 such as a pointing device,it is judged at a branch 901 as YES. Next, it is judged at branches 902to 905 on which component constituting the GUI screen the softwarecomponent was superposed.

If the software component is superposed on the schedule display areacomponent 703 on the GUI screen shown in FIG. 7, it is judged at thebranch 902 as YES, and at a process block 906 the inter-componentcommunication control unit 109 notifies the schedule display areacomponent 112 of the superposed software component. After this notice,the schedule display area component 112 performs a necessary process ata process block 907.

If the software component is superposed on the member select component701, it is judged at the branch 903 as YES, and at a process block 908the inter-component communication control unit 109 notifies the memberselect component 110 of the superposed software component. After thisnotice, the member select component 110 performs a necessary process ata process block 909.

If the software component is superposed on the calendar component 702,it is judged at the branch 904 as YES, and at a process block 910 theinter-component communication control unit 109 notifies the calendarcomponent 111 of the superposed software component. After this notice,the calendar component 111 performs a necessary process at a processblock 911.

If the software component is superposed on the visiting site/work matterincorporating component 801, it is judged at the branch 905 as YES, andat a process block 912 the inter-component communication control unit109 notifies the visiting site/work matter incorporating component 113of the superposed software component. After this notice, the visitingsite/work matter incorporating component 113 performs a necessaryprocess at a process block 913.

Next, a process to be executed by each component constituting the GUIscreen after the inter-component communication control unit 109 notifiesthe superposed software component, will be described.

First, a process 907 to be executed by the schedule display areacomponent 112 after receiving the notice will be described withreference to FIG. 10. After the notice is received, at branches 1001 to1004 a process is selected in accordance with the type of the superposedsoftware component. If the superposed software component is the softwarecomponent 704 or 705 indicating a member in the member select component701, the branch 1001 judges as YES. At a process block 1005 a process isperformed for referring to the schedule of the member indicated by thesoftware component at the default date. The default date is preset inthe default value setting unit 127. If the superposed software componentis the software component 706 indicating a date in the calendarcomponent 702, the branch 1002 judges as YES. At a process block 1006 aprocess is performed for referring to the schedule of the date indicatedby the software component at the default member. The default member ispreset in the default value setting unit 127. If the superposed softwarecomponent is the software component 803 indicating visiting siteinformation in the visiting site/work matter incorporating component801, the branch 1003 judges as YES. At a process block 1007 a process isperformed for setting the visiting site information indicated by thesoftware component as the visiting site of a schedule to be newlyregistered. If the superposed software component is the softwarecomponent 804 indicating work matter information in the visitingsite/work matter incorporating component 801, the branch 1004 judges asYES. At a process block 1008 a process is performed for setting the workmatter information indicated by the software component as the workmatter site of a schedule to be newly registered. If the superposedsoftware component is different from the above-described components, theflow returns to (1) in FIG. 9 without performing any process.

A process 909 to be executed by the member select component 110 afterreceiving the notice will be described with reference to FIG. 11. Afterthe notice is received, at branches 1101 to 1102 a process is selectedin accordance with the type of the superposed software component. If thesuperposed software component is the software component 708 or 709indicating a member in the schedule display area component 703, thebranch 1101 judges as YES. At a process block 1103 a process isperformed for deleting the schedule of the member indicated by thesoftware component from the schedule screen 707. If the superposedsoftware component is the software component 710 or 711 indicatingscheduling data in the schedule display area component 703, the branch1102 judges as YES. At a process block 1104 a process is performed forregistering scheduling data having similar contents as those of theschedule indicated by the software component, in the schedule of themember selected on the member select component 701 at the default date.The default date is preset in the default value setting unit 127. If thesuperposed software component is different from the above-describedcomponents, the flow returns to (1) in FIG. 9 without performing anyprocess.

A process 911 to be executed by the calendar component 111 afterreceiving the notice will be described with reference to FIG. 12. Afterthe notice is received, at a branch 1201 a process is selected inaccordance with the type of the superposed software component. If thesuperposed software component is the software component 704 or 705indicating a member in the member select component 701, the branch 1201judges as YES. At a process block 1202 a process is performed forreferring to the schedule of the selected member at the selected date.If the superposed software component is different from theabove-described components, the flow returns to (1) in FIG. 9 withoutperforming any process.

A process 913 to be executed by the visiting site/work matterincorporating component 113 after receiving the notice will be describedwith reference to FIG. 13. After the notice is received, at a branch1301 a process is selected in accordance with the type of the superposedsoftware component. If the superposed software component is the softwarecomponent 710 or 711 indicating a schedule in the schedule display areacomponent 703, the branch 1301 judges as YES. At a process block 1302 aprocess is performed for registering visiting site information and workmatter information of the scheduling data indicated by the softwarecomponent, in the visiting site/work matter incorporating component 113.If the superposed software component is different from theabove-described components, the flow returns to (1) in FIG. 9 withoutperforming any process.

Next, each process selected by each component constituting the GUIscreen will be described in detail.

First, a member schedule reference process 1005 will be described withreference to FIG. 14. Upon being notified from the inter-componentcommunication control unit 109 that the software component 704 or 705indicating a member in the member select component 701 was superposedupon the schedule display area component 703, at a process block 1401the schedule display area component 112 inquires the member selectcomponent 110 about member information of the member indicated by thesoftware component. FIG. 7 shows an example that the software componentindicating “group 1” was superposed upon the schedule display areacomponent 703. In this example, in response to the inquiry, theinformation of the item 4 shown in FIG. 2 is returned to the scheduledisplay area component 112. Next, at a branch 1402 it is judged, fromthe item of the type 203 of the inquired member information, whether themember is an individual or a group. In the example shown in FIG. 7, thetype 203 of the item 4 is referred to so that it is judged that themember is a group.

If the member is an individual, at a process block 1403 the memberinformation of the individual is stored in an array which stores memberinformation of the member whose schedule is referred to. At a processblock 1404 a variable NUM indicating the number of members whoseschedules are referred to is set with “1”.

If the member is a group, at a process block 1405 the member selectcomponent 110 is inquired about member information of all membersbelonging to the group. In the example shown in FIG. 7, in response tothe inquiry, information of the items 5 and 6 having the parent ID 204of “GROUP001” which is the user ID 201 of the “group 1” is returned tothe schedule display area component 112.

Next, at a process block 1408 a variable COUNT for counting the numberof members acquired the scheduling data is set to “0”. At a repetitionprocess 1409, the following processes are repeated by the number ofmembers to be displayed. In the example of FIG. 7, the followingprocesses are repeated twice.

At a process block 1410 the scheduling data containing the user ID ofthe member whose schedule is referred to and the default date isacquired from the scheduling data storage device 105. Next, at a branch1411 it is judged, through comparison between the user ID 201 of themember and the user ID stored in the ID storage buffer 122, whether themember whose schedule is referred to is the user or not. If the memberwhose schedule is referred to is the user, at the branch 1411 it isjudged as YES. At a process block 1412, the operation privileges 401 ofall the acquired user schedules are made valid, and the acquiredscheduling data is stored in the scheduling data storage buffer 120. Ifthe member is not the user, it is judged at the branch 1411 as NO. At aprocess block 1413 the operation privileges 401 of all the acquiredmember schedules are made invalid, and the acquired scheduling data isstored in the scheduling data storage buffer 120.

In the example shown in FIG. 7, the above processes are executed firstfor the item 5. Assuming that the default date is a current date (Oct.28, 1997), at the process block 1410 the scheduling data containing theuser ID 301 of “USER001” and the date 302 of “Oct. 28, 1997”, i.e., theinformation of the item 2 shown in FIG. 3, is acquired from thescheduling data storage device 105. Next, at the branch 1411 it isjudged whether the member is the user. In this case, if “USER001” isstored in the ID storage buffer 122, the member in the item 5 is judgedas the user. Therefore, at the next process block 1412, the “valid”operation privileges 401 are added to all the acquired schedules of themember of the item 5 shown in FIG. 2, i.e., to the information in theitem 2 shown in FIG. 3, and the information in the item 1 shown in FIG.4 is stored in the scheduling data storage buffer 120.

The member in the item 6 in FIG. 2 has the user ID “USER002” which isdifferent from the ID “USER001” stored in the ID storage buffer 122.Therefore, it is judged at the branch 1411 that the member is not theuser. At the process block 1413 the “invalid” operation privileges 401are therefore added to all the acquired schedules of the member of theitem 6 shown in FIG. 2, i.e., to the information in the item 4 shown inFIG. 3, and the information in the item 2 shown in FIG. 4 is stored inthe scheduling data storage buffer 120.

At a process block 1414, the schedule screen 707 for displayingscheduling data is displayed on a schedule display area. Lastly, at aprocess block 1415 the scheduling data stored in the scheduling datastorage buffer 120 is displayed on the schedule screen. In the exampleshown in FIG. 7, at the process block 1415 the scheduling data of theitems 1 and 2 shown in FIG. 4 and stored in the scheduling data storagebuffer 120 is displayed on the schedule screen 707.

In the above description, after the schedule screen 707 is displayed,the scheduling data is displayed. However, the scheduling data may bedisplayed in different ways. Namely, if the schedule display areacomponent 112 has a function of judging a component superposed area andwhen the software component indicating a member is superposed upon thearea where the schedule screen 707 is displayed, the schedules of thenew member may be additionally displayed on the schedule screen 707.Alternatively, if the software component indicating a member issuperposed upon the area where the schedule screen 707 is not displayedon the schedule display area component 703, a new schedule screen 707may be opened and the schedule of the member may be displayed thereon.

A date schedule reference process 1006 will be described with referenceto FIG. 15. Upon being notified from the inter-component communicationcontrol unit 109 that the software component 706 indicating a date inthe calendar component 702 was superposed upon the schedule display areacomponent 703, at a process block 1501 the schedule display areacomponent 703 is inquired about the date information indicated by thesoftware component. For example, if the software component indicatingthe date Oct. 28, 1997 is superposed upon the schedule display areacomponent, the date information Oct. 28, 1997 is returned to theschedule display area component 112 in response to the inquiry.

At a process block 1502 the scheduling data containing a default user IDof the member and the inquired date is acquired from the scheduling datastorage device 105 and the operation privilege 401 is set in a mannersimilar to the schedule reference process, and the acquired schedulingdata is stored in the scheduling data buffer 120. Consider, for example,the case wherein the default member is the user and the user ID is“USER001”. In this case, the scheduling data in the item 2 shown in FIG.3 and having the user ID 301 of “USER001” and the date 302 of “Oct. 28,1997” is acquired. Since the schedule is the user's schedule, theoperation privilege 401 is set to “valid”, and the scheduling data inthe item 1 shown in FIG. 4 is stored in the scheduling data buffer 120.

Lastly, at a process block 1502 the acquired scheduling data isdisplayed on the schedule screen 707. In the above example, thescheduling data in the item 1 shown in FIG. 4 and stored in thescheduling data buffer 120 is displayed on the schedule screen 707.

A process 1007 of setting visiting site information to scheduling datato be newly registered will be described with reference to FIG. 16. Uponbeing notified from the inter-component communication control unit 109that the software component 803 indicating visiting site information inthe visiting site/work matter incorporating component 801 was superposedupon the schedule display area component 802, at a process block 1601the visiting site/work matter incorporating component 113 is inquiredabout the visiting site information indicated by the software component.For example, if the software component 803 indicating “conference roomA” in the visiting site/work matter incorporating component 113 issuperposed upon the schedule display area component 802, the informationin the item 1 shown in FIG. 6A is returned to the schedule display areacomponent 112 in response to the inquiry.

Next, at a branch 1602 it is judged whether a new schedule registrationscreen 805 is displayed on the schedule display area component 802. Ifdisplayed, at a process block 1603 the visiting site informationindicated by the superposed software component is set to a visiting site402 in the scheduling data to be newly registered. The visiting siteinformation is displayed in a visiting site column 806 of the newschedule registration screen 805.

If the new schedule registration screen 805 is not displayed, at aprocess block 1604 an area for new schedule registration is reserved inthe scheduling data storage buffer 120 and an initialization process isperformed. At a process block 1605 the visiting site informationindicated by the superposed software component is set to the visitingsite 402 of the scheduling data to be newly registered. The new scheduleregistration screen 805 with the visiting site 806 being set isdisplayed.

In the above example, at the process block 1603 if the new scheduleregistration screen 805 is displayed, or at the process block 1605 ifnot displayed, the “conference room A” is set to the visiting site 402in the new scheduling data and displayed in the visiting site column 806in the new schedule registration screen 805 as shown in FIG. 8.

A process 1008 of setting work matter information to scheduling data tobe newly registered will be described with reference to FIG. 17. Uponbeing notified from the inter-component communication control unit 109that the software component 804 indicating work matter information inthe visiting site/work matter incorporating component 801 was superposedupon the schedule display area component 802, at a process block 1701the visiting site/work matter incorporating component 113 is inquiredabout the work matter information indicated by the software component.For example, if the software component 804 indicating “progressconference” in the visiting site/work matter incorporating component 801is superposed upon the schedule display area component 802, theinformation in the item 1 shown in FIG. 6B is returned to the scheduledisplay area component 112 in response to the inquiry.

Next, at a branch 1702 it is judged whether the new scheduleregistration screen 805 is displayed on the schedule display areacomponent 802. If displayed, at a process block 1703 the work matterinformation indicated by the superposed software component is set to awork matter 403 in the scheduling data to be newly registered. The workmatter information is displayed in a work matter column 807 of the newschedule registration screen 805.

If the new schedule registration screen 805 is not displayed, at aprocess block 1704 an area for new schedule registration is reserved inthe scheduling data storage buffer 120 and an initialization process isperformed. At a process block 1705 the work matter information indicatedby the superposed software component is set to the work matter 403 ofthe scheduling data to be newly registered. The new scheduleregistration screen 805 with the work matter 807 being set is displayed.

In the above example, at the process block 1703 if the new scheduleregistration screen 805 is displayed, or at the process block 1705 ifnot displayed, the “progress conference” is set to the work matter 403in the new scheduling data and displayed in the work matter column 807in the new schedule registration screen 805.

A process 1103 of deleting a schedule of a member from the schedulescreen 707 will be described with reference to FIG. 18. Upon beingnotified from the inter-component communication control unit 109 thatthe software component 708 or 709 indicating a member in the scheduledisplay area component 703 was superposed upon the member selectcomponent 701, at a process block 1801 the schedule area displaycomponent 112 is instructed to delete the schedule of the memberindicated by the software component from the schedule screen 707.

Upon reception of the instruction, at a process block 1802 the scheduledisplay area component 112 deletes the scheduling data containing theuser ID of the member from the schedule storage buffer 120.

For example, if the software component 709 indicating Mr. B on theschedule screen 707 shown in FIG. 7 is superposed upon the member selectcomponent 701, at the process block 1801 the member select component 110instructs the schedule display area component 112 to delete the scheduleof Mr. B.

Upon reception of the instruction, at the process block 1802 theschedule display area component 112 deletes the scheduling datacontaining the user ID 404 of “USER002” of Mr. B, i.e., the informationin the item 2 shown in FIG. 4, from the schedule storage buffer 120.

Lastly, at a process block 1803 in order to reflect the change contentsof the scheduling data storage butter 120 upon the schedule screen 707,the schedule screen 707 is again drawn. In the above example, at theprocess block 1803 only the schedule of Mr. A is displayed on theschedule screen.

A process 1104 of registering a selected schedule in the scheduling dataof a member will be described with reference to FIG. 19. Upon beingnotified from the inter-component communication control unit 109 thatthe software component 710 or 711 indicating a schedule in the scheduledisplay area component 703 was superposed upon the member selectcomponent 701, at a process block 1901 the member information of themember selected on the member select screen 701 is supplied to theschedule area display component 112. At a process block 1902 theschedule display area component 112 is instructed to register the datahaving the same contents as those indicated by the superposed softwarecomponent, in the scheduling data of the member.

Upon reception of the instruction, at a process block 1903 the scheduledisplay area component 112 reserves an area for member scheduleregistration in the scheduling data storage buffer 120, and aninitializing process is performed. At a process block 1904 the user IDselected by the member select component 701 is set to the user ID 404 ofthe scheduling data. A default date is set to the date 405 of thescheduling data. The default date is preset in the default value settingunit 127. At a process block 1905 the same contents as those of thescheduling data of the superposed software component are set, exceptingthe items of the user ID 404 and date 405 in the scheduling data.Lastly, at a process block 1906 the registered scheduling data of themember is added to the scheduling data storage device 105.

For example, if the software component 711 indicating the schedule ofMr. B on Oct. 28, 1997 on the schedule screen 707 shown in FIG. 7 issuperposed upon the member select component 701 under the condition thatMr. A is selected, at the process block 1901 the member information ofMr. A in the item 5 shown in FIG. 2 is supplied from the member selectcomponent 110 to the schedule display area component 112. At the nextprocess block 1902 it is instructed to register the scheduling data ofMr. B on Oct. 28, 1997 in the item 2 shown in FIG. 4, in the schedulingdata of Mr. A.

Upon reception of the instruction, at the process block 1904 the user ID“USER001” of Mr. A is set to the user ID 404 of the scheduling data tobe newly registered. If the default date is set as the date informationin the selected scheduling data, Oct. 28, 1997 is set to the date. Atthe process block 1905, the scheduling data indicated by the superposedsoftware component 711, i.e., the same contents as those in the item 2shown in FIG. 4, are set excepting the other items. The scheduling dataregistered in the scheduling data of Mr. A is added in the schedulingdata storage device 105 at the process block 1906.

A process 1202 of referring to the scheduling data of a selected memberon a selected date will be described with reference to FIG. 20. Uponbeing notified from the inter-component communication control unit 109that the software component 704 or 705 indicating a member in the memberselect component 701 was superposed upon the calendar select component702, at a process block 2001 the member select component 110 is inquiredabout the member information of the member indicated by the superposedsoftware component. Next, at a process block 202, the member informationand the date 706 information selected on the calendar component 702 aresupplied to the schedule display area component 112. At the next processblock 2003 the schedule display area component 112 is instructed torefer to the scheduling data of the selected member on the selected datein accordance with the supplied information.

Upon reception of the instruction, at a process block 2004 the scheduledisplay area component 112 acquires from the scheduling data storagedevice 105 the scheduling data containing the user ID 301 of theselected member and the selected date 302. Similar to the memberschedule reference process 1005, the operation privilege 401 is added tothe acquired scheduling data to be thereafter stored in the schedulingdata storage buffer 120. Lastly, at a process block 2005 the schedulingdata stored in the scheduling data storage buffer 120 is displayed.

For example, if the software component indicating Mr. A is superposedupon the calendar component 702 selected with the date Oct. 28, 1997, atthe process block 2001 the member select component 110 is inquired aboutthe member information of Mr. Mr. A to obtain the member informationsuch as shown in the item 5 shown in FIG. 2. Next, at the process block2002 the member information of Mr. A in the item 5 shown in FIG. 2 andthe date information of Oct. 28, 1997 selected by the calendar component702 are supplied to the schedule display area component. At the processblock 2003, the schedule display area component 112 is instructed torefer to the scheduling data of Mr. A on Oct. 28, 1997.

Upon reception of the instruction, at the process block 2004 thescheduling display area component 112 acquires from the scheduling datastorage device 105 the scheduling data in the item 2 shown in FIG. 3 andcontaining the user ID 301 of Mr. A and the date 302 of Oct. 28, 1997.The operation privilege 401 is set to the acquired scheduling data in amanner described previously to be thereafter stored in the schedulingdata storage buffer 120. Lastly, at the process block 2005 thescheduling data in the item 1 shown in FIG. 4 and stored in thescheduling data storage buffer 120 is displayed.

A visiting site/work matter registration process 1302 will be describedwith reference to FIG. 21. Upon being notified from the inter-componentcommunication control unit 109 that the software component 710 or 711indicating a schedule in the schedule display area component 703 wassuperposed upon the visiting site/work matter incorporating component801, at a process block 2101 the schedule display area component 112 isinquired about the scheduling data indicated by the superposed softwarecomponent. In accordance with the inquired scheduling data, visitingsite information is first registered and then work matter information isregistered. The order of registering the visiting site information andwork matter information may be reversed.

At a branch 2102 it is judged whether the visiting site of thescheduling data is set and already stored. Only if the both conditionsare met, the visiting site information is registered by the followingprocedure. At a process block 2103 an area for registering the visitingsite information is reserved in the visiting site/work matter storagebuffer 124. At a process block 2104, the visiting site information anduser ID in the scheduling data indicated by the superposed softwarecomponent are stored respectively in a visiting site 602 and a user ID601. At a process block 2105, the registered contents are added to thevisiting site/work matter information storage device 106.

Next at a branch 2106 it is judged whether the work matter of thescheduling data is set and already registered. Only if the bothconditions are met, the visiting site information is registered by thefollowing procedure. At a process block 2107 an area for registering thevisiting site information is reserved in the visiting site/work matterstorage buffer 124. At a process block 2108, the visiting siteinformation and user ID in the scheduling data indicated by thesuperposed software component are stored respectively in a visiting site604 and a user ID 603. At a process block 2109, the registered contentsare added to the visiting site/work matter information storage device106. Lastly, at a process block 2110 the software component indicatingthe registered visiting site information and work matter information isdisplayed on the visiting site/work matter incorporating component 801.

For example, if the software component 710 indicating the schedulingdata of Mr. A on Oct. 28, 1997 displayed in the scheduling screen 707shown in FIG. 7 is superposed upon the visiting site/work matterincorporating component 801, at the process block 2101 the schedulingdata in the item 1 shown in FIG. 4 is supplied to the visiting site/workmatter incorporating component 113. If it is assumed that the visitingsite information of Mr. A shown in FIG. 6A is already registered, thenthe visiting site 402 of the scheduling data in the item 1 shown in FIG.4 is “conference room A” and this information exists in the visitingsite 602 in the item 1 shown in FIG. 6A. Therefore, it is judged as NOat the branch 2102. In this example, therefore, the visiting siteinformation is not registered.

For the work matter registration, if it is assumed that the work matterinformation of Mr. A shown in FIG. 6B is already registered, then thework matter 403 of the scheduling data in the item 1 shown in FIG. 4 is“review” and this information is not stored in the visiting site/workmatter information storage buffer 124. Therefore, it is judged as YES atthe branch 2106. At the next process block 2108 “review” and“USER001”are respectively set to the work matter 604 and user ID 603. Atthe process block 2109, the work matter information is added to thevisiting site/work matter information storage device 106. Lastly, thesoftware component indicating the work matter “review” of Mr. A isdisplayed on the visiting site/work matter incorporating component 801.

The invention is not limited to the above-described embodiment. Forexample, if the software component indicating the date on the calendarcomponent 702 is superposed upon the member select component 701, themember schedule reference process may be selected for the memberselected by the member select component 701 on the date indicated by thesoftware component. This can be achieved by the following procedure. Themember select component 110 inquires the calendar component 111 aboutthe date information indicated by the superposed software component.Next, the inquired date information and the member information of themember selected by the member select component 701 are supplied to theschedule display area component 112. The schedule display area component112 is instructed to perform a process of referring to the schedulingdata of the selected member on the selected date in accordance with thesupplied information. The instructed schedule display area component 112performs a process of referring to the scheduling data of the designatedmember on the designated date.

In the schedule reference process of the above embodiment, although asingle software component is superposed, a plurality of softwarecomponents may be superposed. In this case, the number of superposedsoftware components is not limited. This can be achieved by repeatingthe processes from the branch 1402 to the repetition block 1409 shown inFIG. 14 by the number of times same as the number of superposed softwarecomponents.

In the above embodiment, although the ID storage buffer 122 and defaultvalue setting unit 127 are contained in the schedule display areacomponent 112, it is not necessary to contain them in the scheduledisplay area component 112, but they may be disposed in any area of thesystem.

Also, the scheduling data management unit 121 performs a process of datatransfer to and from the scheduling data storage device 105. This datatransfer unit may be disposed in any area of the system. The sameconfiguration is also applied to the member information management unit115, calendar information management unit 118, and visiting site/workmatter management unit 125.

The layout of the components constituting the GUI screen is not limitedonly to that shown in FIG. 7, but any layout may be applied.

In the above embodiment, a process is selected in accordance with arelation of a software component with components constituting the GUIscreen, the relation being determined from the superposition of softwarecomponents. However, other operations may be applied so long as therelation of a software component with components constituting the GUIscreen can be determined.

In the member schedule reference process, the operation privilege 402 ofscheduling data of a member other than the user is set “invalid”.However, a table storing a relation, for example, a superior officer anda secretary may be prepared and the operation privilege 401 ofscheduling data of the superior officer may be set “valid” relative tothe secretary. Alternatively, scheduling data may be provided with anitem for storing a member who registered the scheduling data in place ofa user, and the operation privilege 401 of scheduling data may be set“valid” relative to the member who registered the scheduling data, inaddition to the user.

As described so far, according to the present invention, main tasks ofthe scheduling management system can be performed with a simpleoperation of superposition of a software component upon a componentconstituting the GUI screen. Further, if the member whose schedulingdata is to be referred to is superposed upon the schedule display area,the schedules of the member can be displayed. Therefore, any user caneasily image and memorize the operations. The invention thus provide asimple and easy-to-memorize operation method so that even a novice usercan learn main operations in relatively short time.

What is claimed is:
 1. A scheduling management system, comprising: ascheduling data storage device for storing scheduling data including adate, a time, and a work matter; a member information storage device forstoring member information including a user ID, a user name, a flagindicating whether the member is an individual or a group, and IDinformation of a hierarchical level the member belongs; a calendarinformation storage device for storing calendar information; a displaydevice for display a GUI screen containing a plurality of components; aninput device for designating an arbitrary position on the GUI screen andentering an operation relative to the designated position on the GUIscreen; and an inter-component communication control unit for, if amovable software component on a certain component constituting the GUIscreen is selected with said input device and is moved and superposedupon another component constituting the GUI screen, notifying the motiondestination other component of the superposed software component;wherein the components constituting the GUI screen include: a calendarcomponent for temporarily storing calendar information acquired fromsaid calendar information storage device in a calendar informationstorage area of said calendar component, displaying a software componentindicating the date in a calendar format on the GUI screen in accordancewith the acquired calendar information, and selecting, if anothersoftware component is superposed upon the software component by saidinput device, a process in accordance with a type of the other softwarecomponent; a schedule display area component for temporarily storingscheduling data acquired from said scheduling data storage device in ascheduling data storage area of said schedule display area component,graphically displaying a software component indicating the schedulingdata in a corresponding area of a schedule screen constituted of a timeaxis and a member axis, in accordance with the acquired scheduling data,and selecting, if another software component is superposed upon thesoftware component by said input device, a process in accordance with atype of the other software component; and a member select component fortemporarily storing member information acquired from said memberinformation storage device in a member information storage area of saidmember select component, hierarchically displaying a software componentindicating the member on the GUI screen in accordance with the acquiredmember information, and selecting, if another software component issuperposed upon the software component by said input device such as apointing device, a process in accordance with a type of the othersoftware component; wherein if the software component indicating thedate on said calendar component is superposed upon said schedule displayarea component by said input device such as a pointing device, saidinter-component communication control unit supplies information of thesoftware component from said calendar component to said schedule displayarea component, and said schedule display are a component judges thatthe software component is a software component of a type that indicatesthe date, to thereby select a process of referring to the schedulingdata of the designated date; if the software component indicating themember on said member select component is superposed upon said scheduledisplay area component by said input device such as a pointing device,said inter-component communication control unit supplies information ofthe software component from said member select component to saidschedule display area component, and said schedule display areacomponent judges that the software component is a software component ofa type that indicates the member, to thereby select a process ofreferring to the scheduling data of the member and judge from theinformation of the software component whether the member is anindividual or a group to perform the selected process; and if thesoftware component indicating the member displayed on the schedulescreen on said schedule display area component is superposed upon saidmember select component by said input device such as a pointing device,said inter-component communication control unit supplies information ofthe software component from said schedule display area component to saidmember select component, and said member select component judges thatthe software component is a software component of a type that indicatesthe member, to thereby select a process of deleting the scheduling dataof the member from the scheduling screen.
 2. A scheduling managementsystem, comprising: a scheduling data storage device for storingscheduling data including a date, a time, and a work matter; a memberinformation storage device for storing member information including auser ID, a user name, a flag indicating whether the member is anindividual or a group, and ID information of a hierarchical level themember belongs; a calendar information storage device for storingcalendar information; a display device for display a GUI screencontaining a plurality of components; an input device for designating anarbitrary position on the GUI screen and entering an operation relativeto the designated position on the GUI screen; and an inter-componentcommunication control unit for, if a movable software component on acertain component constituting the GUI screen is selected with saidinput device and is moved and superposed upon another componentconstituting the GUI screen, notifying the motion destination othercomponent of the superposed software component; wherein the componentsconstituting the GUI screen include: a calendar component fortemporarily storing calendar information acquired from said calendarinformation storage device in a calendar information storage area ofsaid calendar component, displaying a software component indicating thedate in a calendar format on the GUI screen in accordance with theacquired calendar information, and selecting, if another softwarecomponent is superposed upon the software component by said inputdevice, a process in accordance with a type of the other softwarecomponent; a schedule display area component for temporarily storingscheduling data acquired from said scheduling data storage device in ascheduling data storage area of said schedule display area component,graphically displaying a software component indicating the schedulingdata in a corresponding area of a schedule screen constituted of a timeaxis and a member axis, in accordance with the acquired scheduling data,and selecting, if another software component is superposed upon thesoftware component by said input device, a process in accordance with atype of the other software component; and a member select component fortemporarily storing member information acquired from said memberinformation storage device in a member information storage area of saidmember select component, hierarchically displaying a software componentindicating the member on the GUI screen in accordance with the acquiredmember information, and selecting, if another software component issuperposed upon the software component by said input device such as apointing device, a process in accordance with a type of the othersoftware component; wherein if the software component indicating thedate on said calendar component is superposed upon said schedule displayarea component by said input device such as a pointing device, saidinter-component communication control unit supplies information of thesoftware component from said calendar component to said schedule displayarea component, and said schedule display are a component judges thatthe software component is a software component of a type that indicatesthe date, to thereby select a process of referring to the schedulingdata of the designated date; if the software component indicating themember on said member select component is superposed upon said scheduledisplay area component by said input device such as a pointing device,said inter-component communication control unit supplies information ofthe software component from said member select component to saidschedule display area component, and said schedule display areacomponent judges that the software component is a software component ofa type that indicates the member, to thereby select a process ofreferring to the scheduling data of the member and judge from theinformation of the software component whether the member is anindividual or a group to perform the selected process; and if thesoftware component indicating the scheduling data displayed on theschedule screen on said schedule display area component is superposedupon said member select component by said input device such as apointing device, said inter-component communication control unitsupplies information of the software component from said scheduledisplay area component to said member select component, and said memberselect component judges that the software component is a softwarecomponent of a type that indicates the scheduling data, to therebyselect a process of registering scheduling data having contents same asthe scheduling data in the member selected by said member selectcomponent.
 3. A scheduling management system, comprising: a schedulingdata storage device for storing scheduling data including a date, atime, and a work matter; a member information storage device for storingmember information including a user ID, a user name, a flag indicatingwhether the member is an individual or a group, and ID information of ahierarchical level the member belongs; a calendar information storagedevice for storing calendar information; a display device for display aGUI screen containing a plurality of components; an input device fordesignating an arbitrary position on the GUI screen and entering anoperation relative to the designated position on the GUI screen; and aninter-component communication control unit for, if a movable softwarecomponent on a certain component constituting the GUI screen is selectedwith said input device and is moved and superposed upon anothercomponent constituting the GUI screen, notifying the motion destinationother component of the superposed software component; wherein thecomponents constituting the GUI screen include: a calendar component fortemporarily storing calendar information acquired from said calendarinformation storage device in a calendar information storage area ofsaid calendar component, displaying a software component indicating thedate in a calendar format on the GUI screen in accordance with theacquired calendar information, and selecting, if another softwarecomponent is superposed upon the software component by said inputdevice, a process in accordance with a type of the other softwarecomponent; a schedule display area component for temporarily storingscheduling data acquired from said scheduling data storage device in ascheduling data storage area of said schedule display area component,graphically displaying a software component indicating the schedulingdata in a corresponding area of a schedule screen constituted of a timeaxis and a member axis, in accordance with the acquired scheduling data,and selecting, if another software component is superposed upon thesoftware component by said input device, a process in accordance with atype of the other software component; and a visiting site/work matterincorporating component for acquiring visiting site information and workmatter information which is part of the scheduling data from a visitingsite/work matter information storage device, and selecting, if thesoftware component is superposed upon any one of the componentsconstituting the GUI screen by said input device such as a pointingdevice, a process in accordance with a type of the software component;wherein if the software component indicating the date on said calendarcomponent is superposed upon said schedule display area component bysaid input device such as a pointing device, said inter-componentcommunication control unit supplies information of the softwarecomponent from said calendar component to said schedule display areacomponent, and said schedule display are a component judges that thesoftware component is a software component of a type that indicates thedate, to thereby select a process of referring to the scheduling data ofthe designated date; if the software component indicating the visitingsite information on said visiting site/work matter incorporatingcomponent is superposed upon said schedule display are a component bysaid input device such as a pointing device, said inter-componentcommunication control unit supplies information of the softwarecomponent from said visiting site/work matter incorporating component tosaid schedule display area component, and said schedule display areacomponent judges that the software component is a software component ofa type that indicates the visiting site information, to thereby select aprocess of setting the visiting site information indicated by thesoftware component to a visiting site of the scheduling data to be newlyregistered; if the software component indicating the work matterinformation on said visiting site/work matter incorporating component issuperposed upon said schedule display area component by said inputdevice such as a pointing device, said inter-component communicationcontrol unit supplies information of the software component from saidvisiting site/work matter incorporating component to said scheduledisplay area component, and said schedule display component judges thatthe software component is a software component of a type that indicatesthe work matter information, to thereby select a process of setting thework matter information indicated by the software component in a workmatter of the scheduling data to be newly registered; and if thesoftware component indicating the scheduling data on said scheduledisplay area component is superposed upon said visiting site/work matterincorporating component by said input device such as a pointing device,said inter-component communication control unit supplies information ofthe software component from said schedule display area component to saidvisiting site/work matter incorporating component, and said visitingsite/work matter incorporating component judges that the softwarecomponent is a software component of a type that indicates thescheduling data, to thereby select a process of newly registering thevisiting site information and the work matter information owned by thesoftware component.